Downloading and launching an app on a second device from a first device

ABSTRACT

The user experience of application downloading and usage between multiple devices in a network is enhanced. One instance of an app on a first device is able to identify and verify installation and/or execution of a companion app on a second device where the two devices may have entirely different platforms (e.g., smartphone operating system and TV platform). The experience for users who have devices on the same network converge in order to improve the user experience with respect to a particular app. In this manner, an enhanced and efficient means of providing an n-screen experience with the app is enabled; ways that provide synergy between devices on the same network.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and claims priority to U.S. patent application Ser. No. 13/751,821, filed on Jan. 28, 2013, incorporated herein by reference.

TECHNICAL FIELD

An embodiment of the present invention relates generally to software for computing devices and convergence networking of such devices. More specifically, it relates to enabling downloading and executing of software applications on various user devices in the same network.

BACKGROUND

Applications that run on non-traditional computing devices, commonly referred to as “apps,” are now quite widespread and known to many users mostly due to their increasingly prevalent use of smartphones, tablets, and other mobile devices. Apps are presently available on a wide range of platforms, including TVs and PCs. Smartphone users frequently download, install and use apps onto their devices. This practice is becoming increasingly popular as well with tablets. Apps are one of the drivers making these mobile devices more and more popular. Finding an app in an app marketplace or app store and then downloading it onto a mobile device is a straightforward procedure and has now become second-hand nature for a lot of users, particularly younger ones.

However, downloading an app onto a TV has not yet caught on among the general public. People do not generally think of executing an app on their TV, even if they have an app on their smartphone and a companion or compatible app is available. Users simply are not aware that there is a similar app available for download on their TV. Or, the user has already downloaded a similar or companion app on their TV but is unaware that the two apps (e.g., on the phone and TV) executing together can provide an enhanced user experience. In instances where a user thinks about executing an app on a TV, she does it by using a remote control and downloads and executes it directly on the TV.

Convergence among various devices is becoming more popular, especially among devices on a home network that has a TV. Convergence features provide the capability of devices to communicate and, consequently, new mechanisms for deploying apps on other devices within a convergence network would be desirable. There is an increasing desire to have devices on a local network communicate with each other and share information. For example, with apps, there is often a companion app that executes on a compatible device having an entirely different platform. To illustrate, there may be a Hulu app for the TV and for a smartphone, but the user only has the one on her smartphone. However, her experience with Hulu would be better if she could execute the Hulu app for the TV as well. As such, it would be desirable to have two or more companion apps work together with minimal user input to deliver an enhanced user experience for the apps.

SUMMARY

One aspect of the invention is a method of using a device to execute an app on another (second) device, for example, using a smartphone having a particular app to execute a companion app on a TV. The two devices will typically be in two different classes, that is, have different operating systems, platforms, and the like, but this is not required (e.g., each device can be a smartphone, tablet, or TV). The second device is queried by the first device to determine whether there is a compatible or companion app already installed on the second device. If there is, it is then determined whether the companion app is presently running on the second device. If it is not, then a message is displayed on the first device asking whether the user of the first device wants to execute the companion app on the second device. If the user of the first device consents, the companion app is executed on the second device. In one embodiment, there may be a message displayed on the second device stating that another user is causing the execution of an app on the second device. For example, a person watching TV will see a message that another user, via her smartphone, is causing the execution of a companion app on the TV. The program or show that the person is watching on TV will not be interrupted.

Another aspect of the invention is a method of using a first device to execute an app on a second device. The first device queries the second device for a compatible app to see if it is already installed. The user of the first device is prompted as to whether to install the compatible app on the second device. It is then determined whether to install the compatible app on the second device. A request is transmitted to the second device to install the compatible app. The compatible app is then downloaded onto the second device.

BRIEF DESCRIPTION OF THE DRAWINGS

The invention and the advantages thereof may best be understood by reference to the following description taken in conjunction with the accompanying drawings in which:

FIG. 1 is an illustration of a series of displays on two devices connected in a local/home network in accordance with one embodiment;

FIGS. 2A and 2B are flow diagrams of processes for discovering, executing, and downloading a companion app on a second device in accordance with one embodiment of the present invention;

FIG. 3 is a block diagram showing relevant components and modules in a first device in accordance with one embodiment of the present invention; and

FIGS. 4A and 4B are diagrams of a computing device suitable for implementing one or more embodiments of the present invention.

In the drawings, like reference numerals are sometimes used to designate like structural elements. It should also be appreciated that the depictions in the figures are diagrammatic and not to scale.

DETAILED DESCRIPTION

Applications are currently available on a wide range of platforms and devices, including smartphones, tablet devices, mobile gaming devices, computing devices in cars, PCs, and TVs. Users are accustomed to the app download, installation, and usage experience on their handheld and mobile devices, the vast majority of which are smartphones and tablets. Now that convergence features enable communication between all these devices and platforms on a local/home network, new mechanisms described in the various embodiments of the present invention deploy apps among various devices in the convergence network. One example of convergence is allowing the user to launch an app on a TV using a smartphone. The overall goal is that when devices are on the same network, it would be desirable to have synergy among the devices.

Methods and systems for enhancing the user experience of application downloading and usage between multiple devices in a network are described in the various figures. One or more embodiments describe the ability of one instance of an app on a first device to identify and verify installation and/or execution of a companion app on a second compatible device where the two devices may have entirely different platforms (e.g., smartphone operating system and TV platform). The term platform may refer to the application runtime environment provided by the TV. It may be described as a layer above the TV operating system that provides both a runtime environment for generic programming instructions as well as the APIs to interface with specific TV functions, services or devices. In the TV application platform, programmers have a choice of programming, for example, in JavaScript or Flash. There are also APIs to interface with the TV tuner, infra-red remote, WiFi/Ethernet/Bluetooth adapters, cameras, and the like.

One or more embodiments of the present invention deliver more than a mere “split screen” user experience or simple sharing of an app on the devices where one app is executing on a smartphone and another related app is executing on a TV. One or more embodiments describe ways in which the experience for users having their devices on the same network converge in order to improve the user experience with respect to a particular app. In this manner, they deliver an enhanced and efficient means of providing an n-screen experience with the app; ways that provide synergy between devices on the same network.

FIG. 1 is an illustration of a series of displays on two devices connected in a local/home network in accordance with one embodiment. For illustrative purposes, the two devices are a smartphone and a TV. In a first scenario, a smartphone display 102 a shows a Netflix app which the user is browsing. The device is connected to a home network and is in communication with a TV displaying a TV show 102 b. The smartphone discovers that the TV has a companion Netflix app and asks the user if he wants to execute the Netflix companion app on the TV in display 104 a. During this time the TV still displays the TV show 104 b. If the smartphone user gives permission to execute the companion Netflix TV app on the TV, in one embodiment a message as shown in 106 b is displayed on the TV (“Launching Netflix App for TV . . . ” or something similar). Additional information such as the name of the user who gave permission to launch the app may be displayed or the message may be displayed in a side bar or smaller display area while the TV show continues to be displayed.

In a second scenario, the companion app may not be on the second device but one is available from an app download server or other source on the network. In this case, a display such as one shown in 108 a where the user is asked whether he wants to initiate a download of a companion “Netflix for TV” app onto the TV. During this time, the TV continues to display a TV show or other image as shown in 108 b. If the user gives permission to download the companion app, a display such as 110 a on the smartphone indicating that the Netflix for TV app is being downloaded is shown. The TV may display a message such as shown in 110 b (“Downloading Netflix App for TV . . . ”) or a similar message. At download completion the companion app will execute automatically. In an alternative embodiment the TV could prompt the user again for confirmation. As these display images show, most of the processes take place in the background, beginning with discovery of the second device to the launching or downloading of the companion app. The only interaction with the user is seeking permission to perform the launching or downloading activity. In another embodiment, these activities may be done automatically without confirmation from the user. This may be preferable for users who always want to have companion apps downloaded or executed on one or more additional devices on the network. In this scenario, the user will automatically have a convergence experience (multi-screen experience) with the app on his devices.

FIGS. 2A and 2B are flow diagrams of processes for discovering, executing, and downloading a companion app on a second device in accordance with one embodiment of the present invention. At block 202, a user launches an app on a device which has a particular platform and is using the app when the process starts. For ease of explanation, this app is sometimes referred to as the “primary app” (and sometimes referred to as the “first instance” of the app) and the device is referred to as the “first device.” The device, which may be any device capable of executing an application, is connected to a home/local network.

At block 204, the first device discovers a compatible device/platform on the network. This discovery may be done using conventional and suitable protocols such as UPnP, Bon Jour, and the like. A device or platform is compatible if it can execute a companion app to the primary app. At block 206, it is determined whether such a device has been discovered on the network.

If such a device (the “second device”), such as a TV or tablet, is found on the network, control goes to block 208 where the first device queries the second device whether the second device presently has a companion or compatible app (with respect to the primary app on the first device). The second device has a software stack that can handle this type of query or request. The query is sent using a communication protocol as defined or chosen by the developer. It may be a proprietary communication protocol. If no compatible device is found on the network, the discovery process continues in the background and control goes back to block 204.

At block 210, the first device is informed of whether a companion app is already installed on the second device. If a companion app is already on the second device, control goes to block 212. If the companion app is not installed, control goes to block 220 of FIG. 2B. If the app is installed, at block 212 it is determined whether the companion app is presently running on the second device. If it is, the user is already having an enhanced 2-screen, convergence experience with the app and the process ends. If it is not, at block 214, the primary app displays a message on the first device asking the user if he wants to execute the companion app on the second device, such a display is shown in display 104 a of FIG. 1. The code or logic to display this message may be embedded in the primary app presently executing on the first device.

At block 216, the first device determines whether the user accepts the offer (i.e., gives permission to execute the companion app on the second device). If the user does not, the process ends. If the user accepts the offer, a message is sent to the second device and the companion app executes at which stage the process ends. Returning to the path where the companion app is already installed on the second device, the user can begin experiencing app and device convergence on two devices.

Going back to block 210, if the companion app is not installed on the second device, control goes to block 220 in FIG. 2B. At this step the user is prompted as to whether he wants to install a compatible or companion app on the second device, as shown in screen display 108 a of FIG. 1. Part of the process here may also involve checking whether the companion app is available for downloading from a server on the network or from an online source for apps, commonly known as an application store. At block 219, the device checks whether the last user selection for the app was to not install (e.g., “Do Not Install”). If so, control goes back to discovery at block 204. If it was not the last selection by the user, control goes to block 220. Here, assuming the app is available, the user of the first device is prompted about installing it as shown in block 220. At block 222, it is determined whether the user consents to installing the companion app on the second device. If the user does consent or give permission to have the companion app downloaded onto the second device, control goes to block 224 where a request is created and transmitted to the second device using the communication means described above. The request instructs the second device to initialize downloading of the companion app. At this stage the companion app is downloaded onto the second device as shown in displays 110 a and 110 b. In this manner, a device in the local network, such as a TV, downloads a specific app according to instructions sent from another device in the network. In one embodiment, control then goes to block 214 of FIG. 2A. Here the user is asked whether to execute the downloaded app.

At block 222, if the user does not consent to downloading the app, control goes to block 226 where a “do not install” setting is saved as the last user selection. This setting may be checked prior to block 220 where the user is prompted to install the companion app. If this setting indicates that the user previously selected the “do not install” option, he is not prompted again on the same question. The process then loops back to block 204 where the discovery process continues. For example, although the user may not want to install the app on the TV, a tablet may now be discoverable on the network and the same process executing in the background on the primary device will occur for this or any new devices. In this case, the user may want to install the companion app on the tablet.

FIG. 3 is a block diagram showing relevant components and modules in a first device, such as a smartphone, in accordance with one embodiment of the present invention. A first device 302 has a primary app 304 as described above. In one or more embodiments, primary app 304 may contain logic for displaying messages on the first device, such as “Execute Companion App on TV?” or “Executing Netflix App on TV . . . ” and the like. The user may provide input to queries by primary app 304 or other modules in device 302. These inputs may be processed by user input processing module 310. As described above, queries are also made of the second device, such as a TV, for example, to determine whether a companion app exists on the second device, if it does, whether it is executing, and so on. This may be done by logic in a companion app query module 308. First device 302 starts the process of finding a second device and companion app by initiating a discovery process on a local network using a suitable protocol such as UPnP or Bon Jour. This may be performed by network device discovery module 312 or other conventional modules for implementing such protocols. There may also be a network interface component 314 for communicating on the local network.

Through the processes described above, an application running on one class of devices (e.g., smartphone, tablet, or devices having the same operating system or platform) has awareness of a companion application for a second class of devices (e.g., a TV). A device from the first class realizes or becomes aware of the presence of a device from the second class on the same local network and the first device coordinates the download and installation of the companion app enabling communication of the two apps and providing a convergence experience for the user. Described below are variations of the above embodiments and alternative embodiments. Some of the description may repeat certain aspects of the content in FIGS. 1, 2A, and 2B but is provided to support the various illustrations.

In one embodiment, the ability of one instance of an application on a first device to verify an installation of a companion or second instance of the application on a second device is described. Also described is the ability of the first instance on the first device to initiate a download of the companion application on a second device. The first and second devices may be any suitable computing device such as smartphones, tablets, TVs, mobile or stationary gaming devices, and PCs. For example, in one example the process may begin with a first device, such as a tablet, running a first instance of an app. The first device is connected to a local/home network and, in the background, discovers that there is a compatible or suitable second device on the network, such as a TV or PC, and communicates with the second device to exchange data or commands, such as commands relating to a discovery protocol (e.g., UPnP) which allows the first device to discover the second device and find its capabilities, including what apps are installed. The first device then sends a request to the second device to determine whether the second device has a companion or second instance of the (first instance) app running on the first device.

The second device sends a response to the request to the first device, i.e., whether the second device as the companion app installed or whether the server has it available for download. If the second device does not have the companion app and the server has it available for download, the first instance of the app on the first device displays a message or notification to the user. The notification indicates that a companion app is available for the second device and, in the same notification, asks whether the user wants to have the companion app downloaded to the second device from the server or other source.

If the user gives permission or approval to download the companion app, the first device issues a command to the second device to download the companion app from the server. The second device then initiates a download of the companion app after which the second device has the companion app. The first instance of the app initiates the download of a companion instance of the app onto a separate device where all the processes, except seeking permission from the user, execute in the background. The user does not need to explicitly connect to and browse an app store or app market. The mechanism for executing the processes described above can be embedded in any app in order to promote use of a companion app for a second device.

In this manner, app vendors encourage users to install companion apps onto more devices, for which consumers may not have been aware that apps were available. This is most often the case with apps for TVs. As a result of the embodiments described herein, the second device, such as the TV, is likely used more often as an app device. The user is more aware and is more inclined to use convergence apps and have a better user experience with the apps.

To illustrate an embodiment, one device is a smartphone and the other device is a TV. The smartphone is the device being used by a user and has a primary app (also referred to as a client app) that is executing on the smartphone and the TV, in this illustration, already has an app that is a companion app to the primary app on the smartphone. It should be noted that the same relationship can be seen in the other direction, that is, the user is watching TV or the user is using (running) an app on the TV and the TV has the primary app and the smartphone already has a companion app to the primary app on the TV.

Returning to the illustration, the smartphone is running the primary app, and is on the same network as the TV. It discovers that there is a compatible TV in the same network. Here compatible implies it is on the same network and is able to execute apps. The smartphone then “pairs” with the TV. If there are other compatible devices, such as other smartphones or PCs, the smartphone carries out the same process with the other devices. The smartphone then checks via the network whether the TV has a companion app to the app executing on the smartphone. If the TV has a companion app, this fact is transmitted to the smartphone, again via the local network. The primary app on the smartphone then displays a message to the user telling the user that there is a companion app on the TV and asks whether the user wants to launch the companion app. If the user gives approval, the smartphone issues a command to the TV via network protocol (which may be proprietary) to launch the companion app on the TV. The TV launches the companion app. The primary app on the smartphone then communicates with the companion app to provide an enhanced, multi-screen user experience with respect to the app.

As described above, an embodiment of the invention introduces a new mechanism for an app on a first device to discover and launch a companion app on a second device. This may be described as a peer-to-peer communication over a home/local network as described in FIGS. 2A and 2B. It is different from conventional home networking standards because an embodiment of the invention provides a mechanism for proprietary communication between the app on the first device and the companion app on the second device over standard HTTP/HTTPS, UPnP, or other conventional protocols. This mechanism, shown in blocks 204 to 224, is a direct communication mechanism between two devices over the home network, typically a wireless access point, router, or at least a network switch may be involved. Alternatively, the first and second devices could communicate over Bluetooth or Wi-Fi Direct standards which do not require any network infrastructure device. These standard technologies are used to discover and connect to other devices in the home/local network. As a result, embodiments of the present invention can support any device type and are not tied to a specific operating system, platform, or product. The developer can define their own proprietary communication protocol over this standard channel (e.g., using customized JSON, XML messages, and the like).

An embodiment of the present invention introduces a way to identify a second device on the network and have a first device automatically ask the second device whether it has a companion app. The only interaction or communication with the user of the first device that may be needed is a message asking whether the user wants to download or execute a companion app on the second device in order to have a multi-screen app experience. In other embodiments, this is not needed.

The various embodiments enable a primary app on a first device to identify and discover a second device in the network and a compatible/companion app. This identifying and discovering is done in the background while the first device is on and connected to the network. The user of the first device is given the option of downloading and/or launching the companion app on the second device. In this manner, the user enjoys a rich, immersive app experience on multiple devices.

As noted above, the primary computing device in an embodiment of the invention is a TV, but it may be another computing device such as a smart phone, a tablet computer, a mobile device, a PC, and the like. FIGS. 4A and 4B illustrate a generic computing system 400, such as a TV, suitable for implementing embodiments of the present invention. Some of the devices that can be used in the present invention may have other features or components (such as an internal TV turner or an external STB) that are not shown in FIGS. 4A and 4B and not all the components shown in these figures (e.g., the keyboard) are needed for implementing the present invention. As such, FIG. 4A shows one possible physical implementation of a computing system as this term is broadly defined.

In one embodiment, system 400 includes a display or screen 404. This display may be in the same housing as system 400. It may also have a keyboard 410 that is shown on display 404 (i.e., a virtual keyboard) or may be a physical component that is part of the device housing. It may have various ports such as HDMI or USB ports (not shown). Computer-readable media that may be coupled to device 400 may include USB memory devices and various types of memory chips, sticks, and cards.

FIG. 4B is an example of a block diagram for computing system 400. Attached to system bus 420 is a variety of subsystems. Processor(s) 422 are coupled to storage devices including memory 424. Memory 424 may include random access memory (RAM) and read-only memory (ROM). As is well known in the art, ROM acts to transfer data and instructions uni-directionally to the CPU and RAM are used typically to transfer data and instructions in a bi-directional manner. Both of these types of memories may include any suitable of the computer-readable media described below. A fixed disk 426 is also coupled bi-directionally to processor 422; it provides additional data storage capacity and may also include any of the computer-readable media described below. Fixed disk 426 may be used to store programs, data and the like and is typically a secondary storage medium that is slower than primary storage. It will be appreciated that the information retained within fixed disk 426, may, in appropriate cases, be incorporated in standard fashion as virtual memory in memory 424.

Processor 422 is also coupled to a variety of input/output devices such as display 404 and network interface 440. In general, an input/output device may be any of: video displays, keyboards, microphones, touch-sensitive displays, tablets, styluses, voice or handwriting recognizers, biometrics readers, or other devices. Processor 422 optionally may be coupled to another computer or telecommunications network using network interface 440. With such a network interface, it is contemplated that the CPU might receive information from the network, or might output information to the network in the course of performing the above-described method steps. Furthermore, one or more method embodiments of the present invention may execute solely upon processor 422 or may execute over a network such as the Internet in conjunction with a remote processor that shares a portion of the processing.

In addition, one or more embodiments of the present invention further relate to computer storage products with a computer-readable medium that have computer code thereon for performing various computer-implemented operations. The media and computer code may be those specially designed and constructed for the purposes of one or more embodiments of the present invention, or they may be of the kind well known and available to those having skill in the computer software arts. Examples of computer-readable media include, but are not limited to: magnetic media such as hard disks, floppy disks, and magnetic tape; optical media such as CD-ROMs and holographic devices; magneto-optical media such as floptical disks; and hardware devices that are specially configured to store and execute program code, such as application-specific integrated circuits (ASICs), programmable logic devices (PLDs) and ROM and RAM devices. Examples of computer code include machine code, such as produced by a compiler, and files containing higher-level code that are executed by a computer using an interpreter.

Although illustrative embodiments and applications of this invention are shown and described herein, many variations and modifications are possible which remain within the concept, scope, and spirit of the invention, and these variations would become clear to those of ordinary skill in the art after perusal of this application. Accordingly, the embodiments described are illustrative and not restrictive, and the invention is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims. 

What is claimed is:
 1. A non-transitory computer-readable medium that includes a program that when executed by a computer performs a method comprising: receiving, at a first application executing on a first device, information indicative of whether a second application is installed on a second device communicatively connected to the first device; and providing a first screen for display within the first application based on the received information, wherein the first screen presents at least one of an execution action or an installation action performable on the second device that involves the second application.
 2. The non-transitory computer-readable medium of claim 1, wherein the first application is stored on a server, and the first application is downloaded to the first device via a network.
 3. The non-transitory computer-readable medium of claim 1, wherein the computer-readable medium comprises a memory for downloading the first application.
 4. The non-transitory computer-readable medium of claim 1, wherein the first screen presents the execution action for execution of the second application on the second device if the received information indicates the second application is installed on the second device.
 5. The non-transitory computer-readable medium of claim 1, wherein the first screen presents the installation action for installation of the second application on the second device if the received information indicates the second application is not installed on the second device.
 6. The non-transitory computer-readable medium of claim 5, wherein the method further comprises: receiving, via the first screen, a user input directed to the installation action; and in response to receiving the user input, presenting a status of the installation of the second application on the second device.
 7. The non-transitory computer-readable medium of claim 5, wherein the method further comprises: receiving, via the first screen, a user input directed to the installation action; generating a command at the first application corresponding to the installation action; and transmitting the command to the second device to initiate the installation of the second application on the second device.
 8. The non-transitory computer-readable medium of claim 7, wherein the method further comprises: executing the second application on the second device when the installation of the second application on the second device has completed.
 9. The non-transitory computer-readable medium of claim 1, wherein the first application executes on a first platform of the first device that is different from a second platform of the second device.
 10. The non-transitory computer-readable medium of claim 1, wherein the method further comprises: determining whether the second application is executing on the second device if the received information indicates the second application is installed on the second device.
 11. A display apparatus comprising: a network interface for communication; and a processor configured to transmit, via the network interface, information for providing a first screen for display within a first application executing on a first device, wherein the information is indicative of whether a second application is installed on the display apparatus, and the first screen presents at least one of an execution action or an installation action performable on the display apparatus that involves the second application.
 12. The display apparatus of claim 11, wherein the processor is further configured to transmit the information in response to receiving a signal requesting the information.
 13. The display apparatus of claim 11, wherein the processor is further configured to: receive a command from the first device, the command being based on a user input received via the first screen and directed to the at least one of the execution action or the installation action; and in response to receiving the command, presenting at least one of an execution status or an installation status of the second application on the display apparatus.
 14. The display apparatus of claim 11, wherein the processor is further configured to: receive a command from the first device, the command being based on a user input received via the first screen and directed to the execution action; and in response to receiving the command, execute the second application on the display apparatus.
 15. The display apparatus of claim 11, wherein the processor is further configured to: receive a command from the first device, the command being based on a user input received via the first screen and directed to the installation action; and in response to receiving the command, install the second application on the display apparatus.
 16. The display apparatus of claim 15, wherein the processor is further configured to download the second application from a server based on receiving the command from the first device.
 17. The display apparatus of claim 15, wherein the processor is further configured to execute the second application on the display apparatus when installation of the second application on the display apparatus has completed.
 18. The display apparatus of claim 11, wherein the first application executes on a first platform of the first device that is different from a second platform of the display apparatus.
 19. The display apparatus of claim 11, wherein the processor is further configured to perform at least one of: in response to determining that the second application is not installed on the display apparatus, transmit, via the network interface, a first command for the first screen to present the installation action for installation of the second application on the display apparatus; or in response to determining that the second application is not executing on the display apparatus, transmit, via the network interface, a second command for the first screen to present the execution action for execution of the second application on the display apparatus.
 20. A system comprising: at least one processor; and a non-transitory processor-readable memory device storing instructions that when executed by the at least one processor causes the at least one processor to perform operations including: receiving, at a first application executing on a first device, information indicative of whether a second application is installed on a second device connected to the first device; and providing a first screen for display within the first application executing on the first device based on the received information, wherein the first screen presents at least one of an execution action or an installation action performable on the second device that involves the second application. 